Conflicts resolved. Pre-conflict-resultion branch has been tested again at with ci.agent.dynamic as the label: https://ci.adoptium.net/job/Grinder/15435/ (That's a bad idea - it should be ADDITIONAL LABEL otherwise it ignores the platform - testing that (with conflicts resolved) at https://ci.adoptium.net/job/Grinder/15486/

Marking ready for review as an initial pass that can be tested.

Hmm in fact using ci.agent.dynamic as an ADDITIONAL_LABEL doesn't work as the ci.agent.dynamic machines get spun up with the labels: ubuntux86-64x64ci.agent.dynamicsw.os.linuxhw.arch.x86ubuntu2204 and not ci.role.test. Tested with LABEL=ci.role.dynamic again at https://ci.adoptium.net/job/Grinder/15487/ (The previous Grinder one from the last comment got stuck)

Made a temporary change to https://ci.adoptium.net/manage/cloud/Azure/template/test-linux-x64/ to add ci.role.test to the list of labels on the dynamic machines and it worked properly, although the "stuck" Grinder 15486 didn't progress and was still stuck.
I have now reverted that change just in case it causes any side effects that I'm not aware of.

Try different test targets and jdk versions

• https://ci.adoptium.net/job/Grinder/15489/ - sanity.functional
• https://ci.adoptium.net/job/Grinder/15490/ - jdk_net (as those tests would be most likely to fail if config of agent differs from static agents), a few failures
  • com/sun/net/httpserver/ServerStopTerminationTest.java.ServerStopTerminationTest
  • java/net/CookieStoreTest.java.CookieStoreTest
  • java/net/MulticastSocket/NoLoopbackPackets.java.NoLoopbackPackets
  • java/net/MulticastSocket/Test.java.Test

14:45:20  [ JUnit Containers: found 4, started 4, succeeded 4, failed 0, aborted 0, skipped 0]
14:45:20  [ JUnit Tests: found 5, started 5, succeeded 4, failed 1, aborted 0, skipped 0]
14:45:20  
14:45:20  java.lang.Exception: JUnit test failure
14:45:20  	at com.sun.javatest.regtest.agent.JUnitRunner.runWithJUnitPlatform(JUnitRunner.java:149)
14:45:20  	at com.sun.javatest.regtest.agent.JUnitRunner.main(JUnitRunner.java:95)
14:45:20  	at com.sun.javatest.regtest.agent.JUnitRunner.main(JUnitRunner.java:61)
14:45:20  	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
14:45:20  	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
14:45:20  	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
14:45:20  	at java.base/java.lang.Thread.run(Thread.java:1583)

• https://ci.adoptium.net/job/Grinder/15491/ - run sanity.openjdk in parallel across 6 nodes (to check it sends to all dynamic nodes) - looks good, 1 testcase failure out of 1657, java/lang/ProcessHandle/OnExitTest.java

* https://ci.adoptium.net/job/Grinder/15489/ - sanity.functional

PASS!

* https://ci.adoptium.net/job/Grinder/15490/ - jdk_net (as those tests would be most likely to fail if config of agent differs from static agents)

Hmmm 4 test case failures there, 2 of which are in multicast tests.

* https://ci.adoptium.net/job/Grinder/15491/ - run sanity.openjdk in parallel across 6 nodes (to check it sends to all dynamic nodes)

Timeout in OnExitTest in testList_4 - regrind at https://ci.adoptium.net/job/Grinder/15520

Yes, multicast and I believe some testcases may be trying to launch containers, given the output text of failed testcases is saying

14:45:20  [ JUnit Containers: found 4, started 4, succeeded 4, failed 0, aborted 0, skipped 0]
14:45:20  [ JUnit Tests: found 5, started 5, succeeded 4, failed 1, aborted 0, skipped 0]
14:45:20  
14:45:20  java.lang.Exception: JUnit test failure
14:45:20  	at com.sun.javatest.regtest.agent.JUnitRunner.runWithJUnitPlatform(JUnitRunner.java:149)

https://github.com/openjdk/jtreg/blob/master/src/share/classes/com/sun/javatest/regtest/agent/JUnitRunner.java#L149

was going to check if those run 'fine' on a static docker container, if we have one for x64 Linux.

was going to check if those run 'fine' on a static docker container, if we have one for x64 Linux.

100 iteration grinders 15515, 15516 and 15517 on x64 static docker systems all seem to fail.

100 iteration grinders 15515, 15516 and 15517 on x64 static docker systems all seem to fail.

I suspected as much, we may want to figure out how to exclude or skip those testcases in containerized environments.